Conversation
🚀 Build Preview on IPFS ready
|
|
This is great as a specific how-to. Is there another, complementary place we can write about all the ways geospatial users can benefit from IPFS? From live meeting:
|
|
|
||
| Before starting, ensure you have: | ||
|
|
||
| - A Zarr data set for |
| Before starting, ensure you have: | ||
|
|
||
| - A Zarr data set for | ||
| - [Kubo](/install/command-line/) or [IPFS Desktop](/install/ipfs-desktop/) installed on a machine with a public IP |
There was a problem hiding this comment.
machine with a public IP
can we link to a resource to help people check if they have a public IP, or configure one if not?
|
|
||
| 1. **Merkleizes** the folder: converts files and directories into content-addressed blocks with UnixFS | ||
| 2. **Pins** the data locally: prevents garbage collection from removing it | ||
| 3. **Queues providing**: announces to the IPFS network that your node has this data |
There was a problem hiding this comment.
"Queues providing" introduces multiple new terms at once. Would any of these alternates work?
- Broadcasts availability
- Starts providing
- Starts advertising
- Advertises the content
|
|
||
| ## Step 5: Content Discovery | ||
|
|
||
| Users need a way to discover your datasets. Choose an approach based on your needs: |
There was a problem hiding this comment.
| Users need a way to discover your datasets. Choose an approach based on your needs: | |
| Now that your data is available on the public network, the next step is making it discoverable to others. Choose a sharing approach based on your needs: |
|
|
||
| ### Option B: Use IPNS for Updatable References | ||
|
|
||
| IPNS provides a stable identifier that you can update when datasets change: |
There was a problem hiding this comment.
| IPNS provides a stable identifier that you can update when datasets change: | |
| If you want to share a stable identifier but be able to update the underlying dataset, create an [IPNS](https://docs.ipfs.tech/concepts/ipns/) identifier and share that instead. This is useful for datasets that get updated regularly —users can bookmark your IPNS name and always retrieve the latest version. |
(not sure if that's the correct way to link internally)
| ipfs name publish /ipfs/<new-dataset-cid> | ||
| ``` | ||
|
|
||
| Users can subscribe to your IPNS name to always get the latest version. |
There was a problem hiding this comment.
Is this an explicit, persistent "subscribe" function? Or do we recommend using it like an IPFS CID (in which case maybe we should describe this without the word "subscribe")
| 'var_name': {'chunks': (1, 512, 512)} | ||
| }) | ||
|
|
||
| # Total size: 1 × 512 × 512 × 4 bytes (float32) = ~1 MB per chunk |
There was a problem hiding this comment.
| # Total size: 1 × 512 × 512 × 4 bytes (float32) = ~1 MB per chunk | |
| # Total size: 1 × 512 × 512 × 4 bytes (float32) = 1048576 bytes = 1 MiB per chunk |
I would add the "1048576 bytes" explicitly, so that the chunker-size below makes sense (you could search the page for that number and find where it comes from).
|
|
||
| The `--quieter` flag outputs only the root CID, which identifies the complete dataset. | ||
|
|
||
| > **Note:** |
There was a problem hiding this comment.
Empty note, I guess it's some left-over.
| ds = xr.open_dataset( | ||
| "ipfs://bafybeif52irmuurpb27cujwpqhtbg5w6maw4d7zppg2lqgpew25gs5eczm", | ||
| engine="zarr" | ||
| ) |
There was a problem hiding this comment.
A link to ipfsspec would be good.
For those (like me) that aren't that familiar with fsspec, it might be good to add a comment in the code like # after the installation of ipfsspec, `ipfs://` urls are automatically recognized
3 participants
What
Add a new geospatial publishing guide
Preview: https://bafybeiaj6f6pnzpoq4ktj5ubgw4de7fk7fzfixvcj7fipignkdwmo2ubk4.ipfs.dweb.link/how-to/publish-geospatial-data/